Curse

iladin · Dec 03, 2006, 08:51 PM // 20:51

Anyone one else have fps to unplayable levels ONLY when the fighting begins?

Seems to be a graphics problem caused by the skill's graphics.

It also runs fine when windowed but not selected.

I'm going to test to see if weapons cause it right now

included is my network diag

TreeDude · Dec 03, 2006, 09:13 PM // 21:13

Your using VMware? VMware isn't exactly mean't for playing games. Since it is VMware you could make a clean image and install GW on it and see if it is any better.

I have use VMware in the IT field for trouble shooting problem and testing server builds. But never for a game. That is not what it is designed for. You may need to just install XP normal and not through VMware.

Nemon · Dec 04, 2006, 10:54 AM // 10:54

Quote:

Originally Posted by TreeDude

Your using VMware? VMware isn't exactly mean't for playing games. Since it is VMware you could make a clean image and install GW on it and see if it is any better.

I have use VMware in the IT field for trouble shooting problem and testing server builds. But never for a game. That is not what it is designed for. You may need to just install XP normal and not through VMware.

Just because he has VMware installed doesn't mean he is running the game in VM. If he is then blah, but...

The fact it only happens when the game is selected in windowed mode, and the only thing i can think that changes when you deselect the GW window is sound, so perhaps it's a sound problem. Another thing it does is decrease the thread priority of the game to "low" when unselected.

I susspect this is a sound problem tho, your system specs look good.

You could try enabling sounds even when deselected and see if anything changes.

Gorebrex · Dec 04, 2006, 01:57 PM // 13:57

The onboard sound may be the problem. What are your in-game sound settings? Is "Use Hardware" selected? If so, unselect it, and also try lowering your sound settings. If you have the in-game music on, turn it off, and disable the EAX, it will likely help if sound is the problem. It might also be that GW isnt given a higher priority for CPU time by Windows, but check sound first.